Bump cryptography for CVE-2026-69247 - #13
Merged
Merged
Conversation
48.0.1 → 50.0.0. 50.0.0 is the floor for CVE-2026-69247 (HIGH); 49.0.0 would clear CVE-2026-69249 alone. The image scan also flags brace-expansion and ip-address inside the worker's cdxgen tree. Both fixed versions already sit inside the caret ranges their parents declare, so a rebuild should pick them up — this commit is partly an experiment to find out why the last one did not.
… tree CVE-2026-69152 (HIGH) and CVE-2026-69192. Neither is suppressible as unreached — cdxgen passes values read from the scanned repository into glob patterns, and the brace-expansion flaw is an uncatchable OOM. A rebuild does not pick up the fixes despite them sitting inside their parents' caret ranges: these arrive through a platform-gated branch that resolves differently on amd64. Same override pattern as the node-tar swap above, extended to every copy npm hoisted since these are transitive.
The previous commit scoped the sweep to cdxgen's subtree, where both packages are already current — it swept nothing and passed. Both findings live under npm's node_modules. brace-expansion needed a second fix: an older override pinned it to 5.0.8 to clear CVE-2026-14257, and 5.0.8 is what CVE-2026-69152 now names. Pinning a fixed version is not a one-time act.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The image scan started failing on four CVEs after a Trivy DB refresh. None of them come from a code change — main fails the same way if you rerun it.
cryptography48.0.1 → 50.0.0 clears two of them. 50.0.0 is the floor for CVE-2026-69247 (HIGH); 49.0.0 would only clear CVE-2026-69249.The other two —
brace-expansion5.0.8 andip-address10.2.0, both inside the worker's cdxgen tree — are deliberately untouched here. Their fixed versions already sit inside the caret ranges their parents declare (minimatchwants^5.0.8,sockswants^10.1.1), so a rebuild should pull them in on its own. The last CI build did not, and I would rather find out why than paste in override blocks or bump cdxgen blind. This PR rebuilds the image, so its scan answers that.If they clear, nothing more is needed. If they do not, the reason will be visible and the fix can be chosen on evidence.